Usage Note 36697: Group member cannot see shared pages in SAS® Information Delivery Portal
In order to increase performance, a user's group membership is cached the first time that the user logs into the SAS Information Delivery Portal. If a user subsequently is added to a new group, the user will not see pages that are shared with that group until after the cache is cleared.
Generally, a shared page is automatically added to a user's Portal only if it is shared as persistant or as default. A page that is shared as available displays only if the user manually adds it to their Portal view.
If the page that is shared as persistant or default is not showing up, then the cache might need to be cleared by using one of the following two methods.
- Clearing the cache for all users depends on which version you are running.
- If you are running the first maintenance release of SAS Information Delivery Portal (4.2 M1) or a later version, then you can clear the cache simply by logging into the Portal as a Portal Administrator.
- At version 4.2 with no maintenance applied, you must log in as the Portal Administrator and open the properties of a shared page for editing. Without making any changes, click OK.
-
To clear the cache for an individual user, the cache can be cleared from page history settings.
- In version 4.3 and later, the user can log in and select Options ► Tools ► Manage Page History ► Clear history. After clearing the cache, the user must log off and then back in to see the shared group content.
- In version 4.2, the user can log in and select Options ► View Page History ► Clear page cache. After clearing the cache, the user must log off and then back in to see the shared group content.
Note: When running in a clustered environment, each Portal instance maintains its own cache. You must individually clear the cache for each instance.
Operating System and Release Information
SAS System | SAS Information Delivery Portal | Microsoft® Windows® for x64 | 4.2 | 4.2_M1 | 9.2 TS2M0 | 9.2 TS2M2 |
Microsoft Windows Server 2003 Datacenter Edition | 4.2 | 4.2_M1 | 9.2 TS2M0 | 9.2 TS2M2 |
Microsoft Windows Server 2003 Enterprise Edition | 4.2 | 4.2_M1 | 9.2 TS2M0 | 9.2 TS2M2 |
Microsoft Windows Server 2003 Standard Edition | 4.2 | 4.2_M1 | 9.2 TS2M0 | 9.2 TS2M2 |
Microsoft Windows XP Professional | 4.2 | 4.2_M1 | 9.2 TS2M0 | 9.2 TS2M2 |
Windows Vista | 4.2 | 4.2_M1 | 9.2 TS2M0 | 9.2 TS2M2 |
64-bit Enabled AIX | 4.2 | 4.2_M1 | 9.2 TS2M0 | 9.2 TS2M2 |
64-bit Enabled Solaris | 4.2 | 4.2_M1 | 9.2 TS2M0 | 9.2 TS2M2 |
HP-UX IPF | 4.2 | 4.2_M1 | 9.2 TS2M0 | 9.2 TS2M2 |
Linux for x64 | 4.2 | 4.2_M1 | 9.2 TS2M0 | 9.2 TS2M2 |
Solaris for x64 | 4.2 | 4.2_M1 | 9.2 TS2M0 | 9.2 TS2M2 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Usage Note |
Priority: | high |
Date Modified: | 2009-08-25 09:10:05 |
Date Created: | 2009-08-03 12:50:00 |